Comments
-
But since it is fixed with v10.2.339, I assume that no reinstallation is necessary (only the upgrade).
-
@BWC Thanks for the info. I will carry out the update as soon as possible and then I will be curious to see if the versioning display corrects itself. I have also just read the vulnerability list again (https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0019). Do I understand correctly that the Netextender had to…
-
I updated about 100 clients with 10.2.338 exe from mysonicwall.com and all of them show the old version (mostly 10.2.336, some 10.2.337). Also client version at SMA GUI show this (old) version. I hope this will be fixed in a future version.
-
Is it also the case with you that the version number in the client is not updated? Or is this a specific problem for me? The previously installed version is still displayed - regardless of whether it is v10.1.336 or another version... regards, Clemens
-
But from my point of view it would be a good and quick way to distribute security updates for the VPN client. -> Feature request :-)
-
Enhanced audit logging I have already enabled,
-
Thanks for this hint! Syslog is activated and will be send to the syslog server. Do you know of a way to send only these messages to a syslog server? (the others go to another server) I had already read that this should work with the "event profile", but unfortunately I can't get any further.
-
Hello, is there a solution to this problem? I have exactly the same effect with Version 10.2.331 (one user out of about 80). With the previous version 10.2.324 everything works. Kind regards, Clemens
-
Hello, I have a similar problem with some Oracle clients. On Sonicwall packets are dropped with the following message: "DROPPED, Drop Code: 70(Invalid TCP Flag(#1)), Module Id: 25(network), (Ref.Id: _5712_uyHtJcpfngKrRmv) 2:2)" I applied the workaround "Dropped packets because of "Invalid TCP Flag", the option "Enable…